home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000824-20010305
/
000087_news@columbia.edu _Tue Oct 24 11:39:54 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by fozimane.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id LAA02071
for <kermit.misc@cpunix.cc.columbia.edu>; Tue, 24 Oct 2000 11:39:54 -0400 (EDT)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id LAA13162
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 24 Oct 2000 11:39:53 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id LAA13410
for kermit.misc@watsun.cc.columbia.edu; Tue, 24 Oct 2000 11:15:49 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@columbia.edu (Frank da Cruz)
Subject: Re: How to convert US EBCDIC -> CP850 ?
Date: 24 Oct 2000 15:15:47 GMT
Organization: Columbia University
Message-ID: <8t4933$d30$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
"ralf.strandell" <ralf.strandell@silja.com> wrote:
: We need to convert files from "us ebcdic" to cp850.
:
: These files contain mostly names with accented characters.
:
Which means they are not "US EBCDIC" but one of the "other"
EBCDICs (see below).
: Unfortunately those files come from as/400 as "us ebcdic".
: (they should be "finnish ebcdic", or swedish, but this cannot be
: changed without reinstalling the system...)
:
How were the files transferred? Why do you think the encoding
was changed? And if the encoding *was* changed to US EBCDIC,
what happened to the accented letters?
: Now we need a way to convert them either to dos cp850
: or unix 7 bit swedish, either by using "translate" or by
: using any script/program.
:
: Can you help?
:
Sort of... C-Kermit and K95 do indeed have a TRANSLATE command,
but it only works for character-sets that are found on platforms
where these programs run, none of which are EBCDIC-based.
In fact, all the character sets known to C-Kermit and K95 are
either ASCII-based (ASCII, ISO 646, ISO 8859, and various
proprietary 8-bit sets that have ASCII as their lower half), or
else Unicode / ISO 10646. The proprietary sets include the many
PC and Windows code pages (CP437, CP850, CP852, CP1252, etc).
In the EBCDIC (IBM mainframe) world, there is a similar
proliferation of code pages, called Country Extended Code Pages
(CECP), including:
CECP 037 (Original USA EBCDIC)
CECP 237 (Germany)
CECP 238 (Finland and Sweden)
CECP 280 (Italy)
CECP 284 (Spain and Latin America)
CECP 285 (UK)
CECP 297 (France)
CECP 424 (Israel)
CECP 500 (West European Multilingual)
CECP 870 (East European Multilingual)
CECP 871 (Iceland)
CECP 875 (Greece)
CECP1025 (Cyrillic)
CECP1026 (Turkish)
CECP1046 (Arabic)
CECP1112 (Baltic)
CECP1122 (Estonia)
CECP1123 (Ukraine)
Most of these are known to IBM Mainframe Kermit. So if you have your
source files were on an IBM mainframe, you could use IBM Mainframe Kermit
to send them to C-Kermit, Kermit 95, or MS-DOS Kermit to obtain the needed
translations. Of course, you would first have to figure out which of
these CECPs is actually used for your files.
But you don't have an IBM mainframe, you have an AS/400. That's a pity,
because this is one of the very few platforms for which a Kermit program
was never written (volunteers???)
So one method is to move the files (without translation or conversion)
from the AS/400 to an IBM Mainframe, and then use IBM Mainframe Kermit
to transfer them to the target computer, using on the mainframe:
set file character-set cp???
set transfer character-set latin1
and on the receiving computer:
set file character-set cp850
If you can't do that, then Kermit can't help, in which case further
advice would depend on what the target platform is: Windows, UNIX, DOS?
In UNIX, for example, maybe you could use the iconv or recode utilities
(if your computer has them, and if they support the source character set),
or you could build your own translation table and run the files through
the tr program. Depending on how the files were transferred, you might
also need some kind of record-format conversion.
- Frank